src/commands/index.ts (1)

42-49: ⚠️ Potential issue | 🟠 Major

Fire-and-forget here can cause unobserved promise rejections.

At Line 42 and Line 58, context.reply(...) is passed directly to ephemeral(...) and discarded with void. If context.reply rejects, ephemeral rejects before its internal .catch(() => {}), so the rejection is not handled.

🔧 Proposed hardening in src/utils/messages.ts (single fix for all call sites)

 export async function ephemeral(message: MaybePromise<PartialMessage>, timeout = 20000): Promise<void> {
-  const msg = await Promise.resolve(message)
-  await wait(timeout)
-    .then(() => modules.shared.api.deleteMessage(msg.chat.id, msg.message_id))
-    .catch(() => {})
+  await Promise.resolve(message)
+    .then((msg) => wait(timeout).then(() => modules.shared.api.deleteMessage(msg.chat.id, msg.message_id)))
+    .catch(() => {})
 }

Also applies to: 58-58

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/commands/index.ts` around lines 42 - 49, The fire-and-forget use of
ephemeral(context.reply(fmt(...))) can lead to unobserved promise rejections if
context.reply rejects; change call sites (the uses of ephemeral and
context.reply in this file) to ensure the returned promise is handled—either
await the ephemeral(...) call where possible or append a .catch(...) to it so
rejections are observed. Specifically, update the calls that pass
context.reply(...) directly into ephemeral (referencing the ephemeral function
and context.reply + fmt invocation) so that context.reply failures are caught
before being discarded (e.g., await ephemeral(...) or ephemeral(...).catch(() =>
{/*log or noop*/})).